phpwebsite-developers

[Phpwebsite-developers] Wish-list for 1.x core

[Verdon V. <ve...@gm...>]

Hi all :)

I've been fiddling a bit trying to re-write some of my stuff for 1.x  
and have run into a couple walls in core. I'm not saying any of these  
things are wrong, just that they make it difficult for me to realize  
my vision for my mods. I wanted to start a bit of a wish-list of  
things that I need from core. I hope other developers might  
contribute to the list and Matt, if I say something really stupid,  
please correct me ;-)

In no particular order...

* Ability to choose categories in an anonymous submission, and  
therefore outside the mini-admin
* Configurable ability to protect/hide a mods public resources  
(uploaded images/files) from  File Cabinet
* Core image upload function (perhaps added to core/class/File.php)

Does anyone else have anything to add?

Very best regards,
verdon

Re: [Phpwebsite-developers] Wish-list for 1.x core

[Shaun M. <sh...@ae...>]

On 3 Jan 2007, at 14:27, Verdon Vaillancourt wrote:

>
> Does anyone else have anything to add?
>

Add the simple wysiwyg tool from 0.10.3 (unreleased) into 1.0. The  
version we ended up with in CVS is really quite good, edits in place  
and works on all browsers unlike FCK or whatever.

The only thing I'd change is make it use bbcode instead of html (or  
make it selectable)

I've got this to look at myself as there's no way I'm ghetto-ising  
non-Firefox/IE users.


Shaun
aegis design - http://www.aegisdesign.co.uk
aegis hosting - http://www.aegishosting.co.uk

Re: [Phpwebsite-developers] Wish-list for 1.x core

[Verdon V. <ve...@gm...>]

On 4-Jan-07, at 7:35 AM, Shaun Murray wrote:

> I've got this to look at myself as there's no way I'm ghetto-ising
> non-Firefox/IE users.
>
Ya, us Safari users have to stick together ;-)

Re: [Phpwebsite-developers] Wish-list for 1.x core

[Matthew M. <ma...@tu...>]

I can convert it to 1.0.0. Please add it to the featreq list at
sourceforge. BTW, wysiwyg is included with 1.0 in the javascript
directory. May be an older version though. In any case, I can add it as
an editor choice.


On Thu, 2007-01-04 at 12:35 +0000, Shaun Murray wrote:
> On 3 Jan 2007, at 14:27, Verdon Vaillancourt wrote:
> 
> >
> > Does anyone else have anything to add?
> >
> 
> Add the simple wysiwyg tool from 0.10.3 (unreleased) into 1.0. The  
> version we ended up with in CVS is really quite good, edits in place  
> and works on all browsers unlike FCK or whatever.
> 
> The only thing I'd change is make it use bbcode instead of html (or  
> make it selectable)
> 
> I've got this to look at myself as there's no way I'm ghetto-ising  
> non-Firefox/IE users.
> 
> 
> Shaun
> aegis design - http://www.aegisdesign.co.uk
> aegis hosting - http://www.aegishosting.co.uk
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
-- 
Matthew McNaney
Electronic Student Services
Appalachian State University
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] Wish-list for 1.x core

[Shaun M. <sh...@ae...>]

On 3 Jan 2007, at 14:27, Verdon Vaillancourt wrote:

> * Core image upload function (perhaps added to core/class/File.php)

I was thinking about this this morning when working out how http:// 
www.huddletogether.com/projects/lightbox2/ might be used to present  
images in blog or a photoalbum rewrite or in an ecommerce module  
where you want small images in the description but big images, or  
multiple images.

I'd like to see a core Image class instead of bundling into File like  
we used to. Maybe it's parent is File so that there's common  
functions but there's different requirements often such as  
thumbnailing, resizing, watermarking and viewing.

I was also thinking that an 'album' class was needed to manage a  
group of images or maybe this should be able to more generally manage  
a group of files including audio, video and normal files. Then with  
an album core class available it'd be easier to upload, present and  
manage multiple images in a standard way across the modules.


Have a play with lightbox2 btw. It's lovely.


Shaun
aegis design - http://www.aegisdesign.co.uk
aegis hosting - http://www.aegishosting.co.uk

Re: [Phpwebsite-developers] Wish-list for 1.x core

[Verdon V. <ve...@ve...>]

Hi Shaun,

On 5-Jan-07, at 9:02 AM, Shaun Murray wrote:

>
> On 3 Jan 2007, at 14:27, Verdon Vaillancourt wrote:
>
>> * Core image upload function (perhaps added to core/class/File.php)
>
> I was thinking about this this morning when working out how http://
> www.huddletogether.com/projects/lightbox2/ might be used to present
> images in blog or a photoalbum rewrite or in an ecommerce module
> where you want small images in the description but big images, or
> multiple images.
>
> I'd like to see a core Image class instead of bundling into File like
> we used to. Maybe it's parent is File so that there's common
> functions but there's different requirements often such as
> thumbnailing, resizing, watermarking and viewing.
>
> I was also thinking that an 'album' class was needed to manage a
> group of images or maybe this should be able to more generally manage
> a group of files including audio, video and normal files. Then with
> an album core class available it'd be easier to upload, present and
> manage multiple images in a standard way across the modules.

I've come to realize since my initial post that there is a fairly  
good image class in File Cabinet (that's what the Featured Photo mod  
is using and it seems a good example of how it might be used) but  
it's not as complete as what you're describing. I wasn't really  
looking there for 'core' things. I guess that's just semantics and in  
the long run probably doesn't matter where things are located in the  
file system, but I was considering File Cabinet a mod and not core  
(albeit a core module). Another way it might have been handled would  
have been to have put File Cabinet's file and image classes in /core/ 
class/ and I might have found them there. You say tomato and I say   
tomato ;-)

Anywise, I agree that thumbnailing/resizing and watermarking are  
critical functions. BTW... thumbnailing/resizing is still available  
in /core/class/File.php

>
> Have a play with lightbox2 btw. It's lovely.
That is a nice visual effect. Someone has made a mod for zen-cart  
(open source e-commerce solution) that uses it and it's pretty popular.

rgds,
verdon

Re: [Phpwebsite-developers] Wish-list for 1.x core

[Matthew M. <ma...@tu...>]

As Verdon suggested, I'd like the image manager included in File Cabinet
able to handle your suggestions. It has an Image and Document class
built in.

Profiles uses it although I haven't really looked at that module in a
while.

Blog and Web Pages will have a feature to add images outside of the
FCKeditor. I thought people were tired of having the templated image
locations. I was wrong :P Once I get that feature back in, we can
discuss the limitations of File Cabinet and how to proceed.

Thanks,
Matt 

On Fri, 2007-01-05 at 14:02 +0000, Shaun Murray wrote:
> On 3 Jan 2007, at 14:27, Verdon Vaillancourt wrote:
> 
> > * Core image upload function (perhaps added to core/class/File.php)
> 
> I was thinking about this this morning when working out how http:// 
> www.huddletogether.com/projects/lightbox2/ might be used to present  
> images in blog or a photoalbum rewrite or in an ecommerce module  
> where you want small images in the description but big images, or  
> multiple images.
> 
> I'd like to see a core Image class instead of bundling into File like  
> we used to. Maybe it's parent is File so that there's common  
> functions but there's different requirements often such as  
> thumbnailing, resizing, watermarking and viewing.
> 
> I was also thinking that an 'album' class was needed to manage a  
> group of images or maybe this should be able to more generally manage  
> a group of files including audio, video and normal files. Then with  
> an album core class available it'd be easier to upload, present and  
> manage multiple images in a standard way across the modules.
> 
> 
> Have a play with lightbox2 btw. It's lovely.
> 
> 
> Shaun
> aegis design - http://www.aegisdesign.co.uk
> aegis hosting - http://www.aegishosting.co.uk
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
-- 
Matthew McNaney
Electronic Student Services
Appalachian State University
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] Wish-list for 1.x core

[Shaun M. <sh...@ae...>]

On 5 Jan 2007, at 16:14, Matthew McNaney wrote:

> As Verdon suggested, I'd like the image manager included in File  
> Cabinet
> able to handle your suggestions. It has an Image and Document class
> built in.
>

Sounds like a good place to put it.

> Profiles uses it although I haven't really looked at that module in a
> while.
>
> Blog and Web Pages will have a feature to add images outside of the
> FCKeditor. I thought people were tired of having the templated image
> locations. I was wrong :P Once I get that feature back in, we can
> discuss the limitations of File Cabinet and how to proceed.
>

I think people ARE tired of the inflexible fixed templated positions  
but that doesn't preclude being able to use images outside of editors  
like FCKeditor. The idea to escape from templates isn't a bad one.

Couldn't we just add images in some shorthand text format (maybe  
extending BBCode) that pointed to an uploaded image asset that the  
user has uploaded to their own personal filecabinet? and images  
uploaded during a blog item creation process are added into a default  
file cabinet?

eg. [img asset=assetid, align=left|right|center]




Shaun
aegis design - http://www.aegisdesign.co.uk
aegis hosting - http://www.aegishosting.co.uk

Re: [Phpwebsite-developers] Wish-list for 1.x core

[Matthew M. <ma...@tu...>]

> Couldn't we just add images in some shorthand text format (maybe  
> extending BBCode) that pointed to an uploaded image asset that the  
> user has uploaded to their own personal filecabinet? and images  
> uploaded during a blog item creation process are added into a default  
> file cabinet?

File Cabinet does use SmartTags. If you upload an image and clip it you
can use the SmartTag anywhere you like. It looks like this:

[filecabinet:image:1]

SmartTags are flexible and we could alignment, styles, etc. to it as
well.

-- 
Matthew McNaney
Electronic Student Services
Appalachian State University
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] Wish-list for 1.x core

[Verdon V. <ve...@ve...>]

On 5-Jan-07, at 12:58 PM, Matthew McNaney wrote:

>> Couldn't we just add images in some shorthand text format (maybe
>> extending BBCode) that pointed to an uploaded image asset that the
>> user has uploaded to their own personal filecabinet? and images
>> uploaded during a blog item creation process are added into a default
>> file cabinet?
>
> File Cabinet does use SmartTags. If you upload an image and clip it  
> you
> can use the SmartTag anywhere you like. It looks like this:
>
> [filecabinet:image:1]
>
> SmartTags are flexible and we could alignment, styles, etc. to it as
> well.

I quite like the SmartTags. Personally, I'd just use them barebones  
and wrap them in a div or span for styling. I'd avoid using the old  
img align attributes, though I can see the ability to send style or  
border info through the tag to be useful. I guess it just boils down  
to personal working preferences and methods. There's a lot of ways to  
skin a cat!

verdon

Ps. no offense to cat lovers ;-)

Re: [Phpwebsite-developers] Wish-list for 1.x core

[Shaun M. <sh...@ae...>]

On 5 Jan 2007, at 17:58, Matthew McNaney wrote:

>> Couldn't we just add images in some shorthand text format (maybe
>> extending BBCode) that pointed to an uploaded image asset that the
>> user has uploaded to their own personal filecabinet? and images
>> uploaded during a blog item creation process are added into a default
>> file cabinet?
>
> File Cabinet does use SmartTags. If you upload an image and clip it  
> you
> can use the SmartTag anywhere you like. It looks like this:
>
> [filecabinet:image:1]
>
> SmartTags are flexible and we could alignment, styles, etc. to it as
> well.


Cool. I presume the SmartTag knows about the asset type so presents  
it in an appropriate way? Then all we need do is expand the types to  
add audio, video, YouTube link etc.


As Verdon said, maybe just let users format the image by wrapping it  
in a div. If they've got a wysiwyg editor, even , the old js one,  
then it's easy enough.

Now it just needs an easy upload facility for getting the image into  
a users personal filecabinet at the time the user is writing the blog  
entry.


Shaun
aegis design - http://www.aegisdesign.co.uk
aegis hosting - http://www.aegishosting.co.uk