dreamingmind / bindery Goto Github PK
View Code? Open in Web Editor NEWCakePHP 1.3 Based Dreaming Mind Bindery Site
CakePHP 1.3 Based Dreaming Mind Bindery Site
CakePHP is a rapid development framework for PHP which uses commonly known design patterns like Active Record, Association Data Mapping, Front Controller and MVC. Our primary goal is to provide a structured framework that enables PHP users at all levels to rapidly develop robust web applications, without any loss to flexibility. The Cake Software Foundation - promoting development related to CakePHP http://cakefoundation.org/ CakePHP - the rapid development PHP framework http://www.cakephp.org Cookbook - user documentation for learning about CakePHP http://book.cakephp.org API - quick reference to CakePHP http://api.cakephp.org The Bakery - everything CakePHP http://bakery.cakephp.org The Show - live and archived podcasts about CakePHP and more http://live.cakephp.org CakePHP TV - screen casts from events and video tutorials http://tv.cakephp.org CakePHP Google Group - community mailing list and forum http://groups.google.com/group/cake-php #cakephp on irc.freenode.net - chat with CakePHP developers irc://irc.freenode.net/cakephp
When a session expires (how long is that? how does that work?) unauthorized page access just throws an error. It needs to redirect to a login page or at least show some error message on a properly rendered page
Though the show/hide javascript on the fieldset legends works great, it produces highly repetitive inline code. This can be cleaned up with a little effort
A layout is needed and it should take Detail Collections into account. This may be a good place for other—as yet undefined—Collection level editing
This is the search box in the upper right of a gallery or on-the-bench page. It should let the user navigate to any image in the set.
Thoughts about page initialization after processing the jump are touched on in the prev/next clicker issue
This may just be a bad data problem. It was a while before I got creation, modified and exif dates recording properly
Using multi-add form to manually upload files the fields width, height and date fields are not getting set. Files that are processed through the upload folder are working properly though.
If the there are multiple forms on the page and the fieldsets are repeated in each form, the id attributes won't be unique. This is not good form and it could limit javascript features that might control the forms. Each fieldset gets a UUID to help with the show/hide attribute and this could be used to solve things though it's very long!
It appears that when I had two Image records linked to the same image and requested one be deleted but that the image be left intact, the thumbnails were deleted but the native image was left alone
the uri is getting updated for the clicker (properly) then the link is followed. The result is you always jump two images and the clickers point to the image you clicked from, not the one you're on.
The process needs to be reversed and I need to insert step 3:
possibly tuning off the natural behavior of these <a>
tags will let me control the order of action.
One idea that keeps tempting me:
The problem would be when the page turns. The thumbnail to click would not be on the page.
What about, rather than activating the thumbnail click, just go to the link then run the corresponding .active-setting routines? When the page turns, all the normal initialization happens (except possibly when you get there via previous).
That suggests the page initialization needs to improve. In fact, it will need the same improvement for Jump Box navigation which will land on an arbitrary thumbnail.
On Image admin pages, putting an digit or digits in the search box will set a number of blank upload forms to draw or trigger the return of an upload set. The regex that does this will respond to numbers embedded in a string too. This isn't great. It means you can't search for content based on any search with a number in it. This shouldn't be too big a deal, but fixing the regex in doSearch() is all it will take to correct it.
Because the target action ($this->searchAction) is being set from the current action in beforeFilter(), two searches in a row will loose the intended target action (set in the hidden field of the search form). It looks like I'll have to go back to an action-by-action setting strategy. Probably a new setter method which each action can call.
Change Workshop->upcoming_session property so it has the structure you proposed
[0]
---Workshop
------workshop_fields
------Session
---------session_fields
------Dates
---------date_fields
------Session
---------session_fields
[1]
---Workshop
--- ...
instead of the current
[0]
---Session
------session_fields
------Dates
---------date_fields
---Workshop
------workshop_fields
[1]
---Session
------session_fields
It would also be nice to have this index by Workshop id like the other properties.
This would probably be easiest by changing the query. Right now we query Session directly and since Session belongsTo Workshop, they come into the array at the same index level.
If you query Workshop, it will haveMany Sessions, so those will be at the next level, grouped under their workshop.
Reference page for doing queries:
http://book.cakephp.org/1.3/en/The-Manual/Developing-with-CakePHP/Models.html
in the section Retrieving Your Data
It would be nice to have a javascript clicker to change the image display sizes. On this form, the full-res image is backing things up so it should be a simple DOM tweak.
This would tell me what forms to put on what pages.
Last upload, Orphan and New links get their values before any saves get done so the values can be wrong. Possibly doing the calcs could be done in the afterFilter() rather than the beforeFilter() as they are now.
nuf said
This is so I can put together direct-link custom galleries to send to customers. I'd like something that was more on-the-fly than full Collection creation although that should be supported also. So this is most likely an alternate to the search box. That is: param would be handled as though you were on the news_feed page and type a search request for param.
Image admin pages have some partially successful behavior like this but I really got lost in the logic. The core strategy at that time seemed to be:
Do some pre-doSearch() logic that looks for the url param and massages things around so it falls into the normal stream of a search request.
Need a client layout for workshops
This should be a solid solution for user searches. Possibly it will present a nice grouped result-page with Site/Policy, Collections and Content sections.
The returns on Site/Policy content would tend to be short and the requests for this rare, but if someone is looking for info about the company, it should be easy to get, so list it first.
The Collections returns will be links to gallery and newsfeed collections that contain content with the relevant term. Possibly highlights for the Collections that MATCH the term?
The Content is as list of specific content items that match so the user could get to a sought after element without sifting through a parent collection. What about turning this found-set into a temporary collection? Or caching it and creating some form of temporary menu so the user can keep peeking at entries with the found set still at hand?
It would be nice to have an ajax tool that re-fetched image EXIF data. This data has gotten lost due to bugs, but even after the bugs are fixed it could get accidentally changed or an image could be changed directly in the native folder? Well... At the very least it would serve for data clean-up even if it was later unneeded.
These elements are drifting off to the right edge of whatever window size. They should stay anchored at the right, above the last thumbnail
also This should be some really simple solution just to get the site off the ground.
The existing purchase page grids need to be folded into the new environment with the least possible disruption to the tables and layout.
There are a couple of required changes:
Add a field for the optional entry of an email address (and session-ize it for convenience)
Improve the message that is assembled from the user's form choices.
If the user provides an email address and submits the form, send them a copy of the order message too.
Make the quote price update live via javascript
This page allows upload of new images and allows replacement uploads for disallowed files found in the upload folder. But it should also work with the search tool to get a set of existing Image records so new pictures can be swapped in to back up the image record. Without this feature, changing an image would be a horror-show of upload/creation, link-recreation/re-sequencing, deletion... ugh.
This relates to the 'stumble footed' issue because it puts more pressure on the search integration.
Revealing an form for an Image in the image_grid layout and pressing the submit button creates a new Content record that has no data (beyond id and dates) and is linked to no Image record.
Titles for images should probably be somewhat standard to create groups that will have good search keywords. There should be a recent-title list available on image intake pages to help with this standardization.
Several times I've wondered if this should be a phase one feature or not. It feels like there are deep implications for the data management, retrieval and display, and that it would be a mistake not to consider these issues early on. At the very least some plan for how this will work needs to be developed at phase one so no serious roadblocks get institutionalized.
url was showing Array as 'pass' param... what? this showed up when on Art & Editions (but not in every circumstance? wierd)
next image button was missing. This showed up when going to Amending Self when no page or id is in the url
views/images/new_uploads has two problems:
1 - the select list for 'Recent Titles' is not getting populated (multi_add is correct and could serve as a model).
2 - when the data is saved, the date field in the EXIF data is being lost. This is important data and very hard to re-discover.
The Fieldset Helper works well. The Elements can transform it into nice, portable, Create/Update modules. But things fall apart when data gets back to the Controller. The way I'm using them now, I'm doing detailed post processing right in the action. But that means if the Element/Helper gets used in another page/context (which is the whole point), I have to re-write all that post-processing.
So I guess, for each Element, there should be a method that can handle the data structure and options unique to that implementation of the Fieldset. Then, each action that is putting Element/Fieldset tools in Views can call the matching set of post-processing methods when data comes back.
The E/F could even set and return an identifier flag so the action could just send the data to a scanner that decides what file-blocks are in play, runs the proper post-processors, and vioa!
At a minimum, the old grid-based page needs to be brought in. But the new interactive page would be MUCH BETTER if I can resolve the interface/animation problem that causes lack of clarity. Specifically, clicking on a material choice in the film strips scrolls the choice to the center of the strip. But the animation is instant making it impossible to understand how the selector has changed. And the visual cues for 'selected item' in the filmstrip are poor.
No matter which layout I bring in, it should be re-written to pull images from the standard Image/Collection system.
Gallery pages should have edit field to update their data including the position of the text on the image, deletions and Collection memberships.
On image grid submit, we jump to the last uploads set rather than the current found set. Appears to be some debug lines left in the code related to the form's submit flash messages.
are the forms staying in place and taking up space for some reason?
There are hidden clickers on the left for this but they don't do anything.
This may have been a 'bad data' annomoly, but it should be checked out.
These pages have an Edit button to let admins tweak the content, but there needs to be more linked data fields in the form so real work can be done. And how about deletion too? or removal from a collection?
Also basic user search and image-grid slugs The search box on Image admin pages only searches Image.alt. This isn't good enough for general work. Either make it more comprehensive or add some other search tools somewhere.
One specific need: finding all the images in a collection.
The rules for having these fields managed are here:
http://book.cakephp.org/1.3/en/view/1002/Creating-Database-Tables#created-and-modified-1015
I'm not 100% sure my data fields default to NULL as required, and I'm sure I am passing in $this->data->Model-name->modified in many or most cases. Unsetting this element is a good starting point.
After creating a new image with two Content records, both linked to different Collections, only the first Collection is showing up on the Tags list in newsfeed. This suggests that the list compiler isn't looking past the first Content record to build the list.
This list should be links to other collections that the contain the Content
another useful property of Workshop would be current_workshop. A query, probably looking at first_day and last_day of Session.
Though properties exist to make found-sets and page drawing parameters persistent and portable between Image actions, there is no consistent plan for the sequence of events that should take place to make the actions and views properly use the resources available.
Specifically at this point, clean-up can't be entered from another view while maintaining the found set. image-grid seems more stable in this regard. And multi-upload is ignorant of the properties altogether. Though it can present upload forms to replace disallowed images, it would be useful to have a way to upload replacement image files for existing image records. This layout would be a logical starting point.
Either just show the darned things or do the fancy fade-in/out javascript
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.