Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#169 2006-05-11 13:04:39
Re: Improving TXP Image Management
Marios,
I think these are good questions you raise.
I’m not totally sure how to address them, except to say that the “issue” or “problem” you raise can be addressed in the write up and see what the devs want to do with it? Alex has started on the write up, and if I have some time this weekend I will add to it. Its hard to know whether its better to take huge steps or giant leaps, but I do know that the devs will be concerned with backward compatability as usual (and for good reason I think), and so without knowing what those parameters are its hard to say how drastic a change to the current conventions are reasonable?
Any coders care to weigh in on that?
Matthew
- I am Squared Eye and I
am launchinghave launched Pattern Tap
Offline
#170 2006-05-11 15:29:42
- guiguibonbon
- Member
- Registered: 2006-02-20
- Posts: 296
Re: Improving TXP Image Management
The proposition for a more powerfull image tag already adresses this issue with a image_name attribute, no? Or maybe I didn’t really understand your problem, Marios.
Now, guys, I thought about something else, wouldn’t a “live search” feature be interesting in the image-browser? Rather than using radio-buttons for categories, names, ids and everything?
Last edited by guiguibonbon (2006-05-11 15:31:27)
Offline
#171 2006-05-11 15:44:04
Re: Improving TXP Image Management
The image_name attribute was intended to reference the image name in TXP not the filename, since TXP does not maintain filenames. However I think by default the filename is placed as the image name on import, if not that could be adjusted as part of the image import process.
There is no uniqueness enforcement for image names in TXP right now (that I know of) so that’s something that needs to be thought about in order to fully use image_name as a selection option, at the very least predictable behaviors in case of conflict should be determined. Of course a uniqueness check could be done on import similar to how url-title duplicates are handled.
I like the live search idea a lot.
Shoving is the answer – pusher robot
Offline
#172 2006-05-11 16:44:48
- guiguibonbon
- Member
- Registered: 2006-02-20
- Posts: 296
Re: Improving TXP Image Management
Well yes, that’s what I meant. Is there no uniqueness check for the images at the moment? Then what good are those image names anyway? Good thing you like the live search, I think Ajax is something that will become hard to avoid. Thought of something else concerning image exploration : it would be a nice thing if the thumbnails displayed could be resized at a maximum width, for I tend to use large thumbnails (460px), so things get quite messy. The WP-way is one solution, or an overflow:hidden div around the images.
I also looked a little closer at that advanced txp:image suggestion, and there are a few points that strike me:- how is the custom-height and custom-width supposed to work? Wouldn’t those rappidly become a web-space disaster (creating many unused thumbs) ?
- all the show_something attributes : why would anyone ever not want to show the width/height, or the alt, or the title? And if ever that would occur, wouldn’t a form give enough freedom? This is just in a concern of keeping things simple.
Offline
#173 2006-05-11 18:55:09
Re: Improving TXP Image Management
guiguibonbon wrote:
- how is the custom-height and custom-width supposed to work? Wouldn’t those rappidly become a web-space disaster (creating many unused thumbs) ?
Web space could be a big issue there. I thought of it more as an image cache, so instead of creating x number of thumbnails with different sizes like what your mockup showed (this was the original idea BTW) you would be able to specify what size you wanted your thumbnail when you actually use it, the thumb would be generated on the fly and cached. Essentially you would only create thumbnails in sizes you actually use, and you could “clear thumbnail cache” to remove any ones generated during testing or something.
This would eliminate the situation when you need a variant size for only specific instances. The main goal was to offer different sizes other then the one thumbnail size. How it’s managed is open to discussion, I think your proposal is equally if not more workable, although I could see maybe needing more then 3 sizes. EZ-publish automagically created large,medium, and small thumbs but it also allowed you specify custom sizes. I have to recheck how that worked.
This was just one idea that came out of a different discussion at one point.
- all the show_something attributes : why would anyone ever not want to show the width/height, or the alt, or the title? And if ever that would occur, wouldn’t a form give enough freedom? This is just in a concern of keeping things simple.
This is just what upm_image offers, and it is currently the closest thing to this that is out there. I think it does that though because it doesn’t force you into a form. If we made <txp:image>
have a default form that is editable like <txp:article>
and <txp:linklist>
we could probably get rid of them. I think they are kind of unnecessary but I’m sure all those that use it would disagree with me.
Definitely don’t take anything in the wiki page as set in stone. It was put up there to generate exactly these types of questions so we can figure out what we need and try to narrow it down to a concrete set of requirements instead of everyone re-phrasing things all the time.
Last edited by hakjoon (2006-05-11 18:55:43)
Shoving is the answer – pusher robot
Offline
#174 2006-05-14 20:57:41
- firago
- Member
- Registered: 2005-01-03
- Posts: 54
Re: Improving TXP Image Management
I use photos in my
* css stylesheet * personal blog to help prove a pointThese are what I think are limitations in the current TXP system of handling/posting images
* that you have to use the numbers that TXP assigns to the images, instead of the title you choose for the imageI would like to see the following functionality
* It would be great if TXP could allow you to call to the images as the title you make for them, not the number TXP assignsI would like to help think through the implications of such functionality in this way
* round of drinks for people who give a crapOffline
#175 2006-05-15 18:59:46
Re: Improving TXP Image Management
Offline
#176 2006-05-15 19:05:44
Re: Improving TXP Image Management
jameslomax,
Great plugin. I think it would be worth asking folks what they think about it.
Well, how about it. What do people see as the strengths and weaknesses of this plugin?
Thx.
M
- I am Squared Eye and I
am launchinghave launched Pattern Tap
Offline
#177 2006-05-15 19:23:47
Re: Improving TXP Image Management
This really looks interesting, James.
One update concerning nhn_image_organizer
: I’m working on some static HTML pages to simulate the possible features of the plugin. But the development is going very slowly because I’m still working on my final thesis at university…
Nils
Offline
#178 2006-05-15 19:27:02
Re: Improving TXP Image Management
Nils,
Let us know how we can help, and focus on your studies! Not on we the sqeeky wheel. Blessings as you write.
M
- I am Squared Eye and I
am launchinghave launched Pattern Tap
Offline
#179 2006-05-15 20:59:04
Re: Improving TXP Image Management
I’m working on some static HTML pages to simulate the possible features of the plugin.
Just as a teaser:
There are now two different views that you can switch by clicking one of the icons in the upper right corner:
- a list view
- and a thumb view
The screenshot shows the second one ;o)
Nils
Offline
#180 2006-05-15 22:43:46
Re: Improving TXP Image Management
What I like about the WP plug in is the way image management is beautifully integrated. There’s no seperated click-this-tab-to-upload-then-click-this-tab-to-save-then-click-this-tab-to-insert workflow; something I’ve referred to before re. the difference between image navigation and image insertion into articles: two different functions that need to be integrated; my suggestion was a more sophisticated bas_image_selector
Also, I like the option to upload either a) one image or b) and entire directory of images. I guess the next step, for txp, is how those multiple images are assigned an identity so they can actually be used. Is this an inherent weakness of txp behaviour? – its certainly a weakness of its image management.
Last edited by jameslomax (2006-05-15 22:49:01)
Offline