[campsite-dev] WHAT NEXT object - Newscoop Development Discussions on Sourcefabric Forum

import

paul's mentioning of image upload and link before they are present in the
htmlarea window brings me some suggestion for the future.

an object by the name of 'whatnext?'

if i go to the image uploader and upload an image, the last screen at the
moment would be:
"Image successfully uploaded"
and you have to click OK
(we will get rid off all those confirmation clicks, ok?)

the object 'whatnext' will be called and it does the following:
the image upload module says:

- i have an image id in mind

so 'whatnext' will match this with all system wide modules of campsite. and
for example the article module says:

- if there is an image id in mind, please offer: 'link image to article'
(with the following URL parameters)

this way there would be an inherent logic and mechanism for the 'next' task
after any taks in the system. the system itself would map the possible next
steps and each new module in campsite needs to have a little extra
specification.

the nice thing: if you don't do the extra work of this specification, you
just don't or add it later. the only damage: the action does not show up,
no errors.

for the future: this would also define the RIGHT MOUSE CLICK on items...

what do you think?

Micz Flor - micz@mi.cz

content and media development http://mi.cz
-----------------------------------------------------------------
http://www.campware.org -- http://crash.mi.cz -- http://suemi.de
"I told our marketing guys to speak now or forever be silent."
(Aleksandar Brajanoski)
-----------------------------------------------------------------

------------------------------------------
Posted to Phorum via PhorumMail

import

Hi Micz,

This is a very good idea but I would call it differently: actions related to
objects. At least for me it would be easier to think this way. When I had an
object (image) I ask what actions are related to it: edit image
metainformation, link image to article.

Mugur

--- Micz Flor wrote:

> paul's mentioning of image upload and link before they are present in the
> htmlarea window brings me some suggestion for the future.
>
> an object by the name of 'whatnext?'
>
> if i go to the image uploader and upload an image, the last screen at the
> moment would be:
> "Image successfully uploaded"
> and you have to click OK
> (we will get rid off all those confirmation clicks, ok?)
>
> the object 'whatnext' will be called and it does the following:
> the image upload module says:
>
> - i have an image id in mind
>
> so 'whatnext' will match this with all system wide modules of campsite. and
> for example the article module says:
>
> - if there is an image id in mind, please offer: 'link image to article'
> (with the following URL parameters)
>
> this way there would be an inherent logic and mechanism for the 'next' task
> after any taks in the system. the system itself would map the possible next
> steps and each new module in campsite needs to have a little extra
> specification.
>
> the nice thing: if you don't do the extra work of this specification, you
> just don't or add it later. the only damage: the action does not show up,
> no errors.
>
> for the future: this would also define the RIGHT MOUSE CLICK on items...
>
> what do you think?
>
> Micz Flor - micz@mi.cz
>
> content and media development http://mi.cz
> -----------------------------------------------------------------
> http://www.campware.org -- http://crash.mi.cz -- http://suemi.de
> "I told our marketing guys to speak now or forever be silent."
> (Aleksandar Brajanoski)
> -----------------------------------------------------------------
>
>

__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo

------------------------------------------
Posted to Phorum via PhorumMail

import

At 12:36 26.01.2005, you wrote:
>Hi Micz,
>
>This is a very good idea but I would call it differently: actions related to
>objects. At least for me it would be easier to think this way. When I had an
>object (image) I ask what actions are related to it: edit image
>metainformation, link image to article.

but i would like to think the other way around.

not: dear object (image) please list what actions are related to you

because this would mean that for example the possible actions for the image
are all set and known.

i would like to think the other way around:

each module / action in the system (now and in the future) defines what it
can do to other objects given what parameters.

then the system checks with the current object (image) what it knows about
itself (id, date, format)

and matches these two to make a list of 'next actions' available.

the advantage:

if someone writes for example a javascript image editor with the possiblity to

a) resize image
b) change color to black and white
c) change jpeg to png

the author of this module does not need to change the configuration of the
image uploader. the new module only needs to say:

IF there is an image object, just give me the ID and i can do the following:
...

>Mugur
>
>--- Micz Flor wrote:
>
> > paul's mentioning of image upload and link before they are present in the
> > htmlarea window brings me some suggestion for the future.
> >
> > an object by the name of 'whatnext?'
> >
> > if i go to the image uploader and upload an image, the last screen at the
> > moment would be:
> > "Image successfully uploaded"
> > and you have to click OK
> > (we will get rid off all those confirmation clicks, ok?)
> >
> > the object 'whatnext' will be called and it does the following:
> > the image upload module says:
> >
> > - i have an image id in mind
> >
> > so 'whatnext' will match this with all system wide modules of campsite.
> and
> > for example the article module says:
> >
> > - if there is an image id in mind, please offer: 'link image to article'
> > (with the following URL parameters)
> >
> > this way there would be an inherent logic and mechanism for the 'next'
> task
> > after any taks in the system. the system itself would map the possible
> next
> > steps and each new module in campsite needs to have a little extra
> > specification.
> >
> > the nice thing: if you don't do the extra work of this specification, you
> > just don't or add it later. the only damage: the action does not show up,
> > no errors.
> >
> > for the future: this would also define the RIGHT MOUSE CLICK on items...
> >
> > what do you think?
> >
> > Micz Flor - micz@mi.cz
> >
> > content and media development http://mi.cz
> > -----------------------------------------------------------------
> > http://www.campware.org -- http://crash.mi.cz -- http://suemi.de
> > "I told our marketing guys to speak now or forever be silent."
> > (Aleksandar Brajanoski)
> > -----------------------------------------------------------------
> >
> >
>
>
>
>
>__________________________________
>Do you Yahoo!?
>Take Yahoo! Mail with you! Get it on your mobile phone.
>http://mobile.yahoo.com/maildemo

Micz Flor - micz@mi.cz

content and media development http://mi.cz
-----------------------------------------------------------------
http://www.campware.org -- http://crash.mi.cz -- http://suemi.de
"I told our marketing guys to speak now or forever be silent."
(Aleksandar Brajanoski)
-----------------------------------------------------------------

------------------------------------------
Posted to Phorum via PhorumMail

import

--- Micz Flor wrote:
> not: dear object (image) please list what actions are related to you
>
> because this would mean that for example the possible actions for the image
> are all set and known.
I didn't mean that; actions may be dynamically registered.

Mugur

__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail

------------------------------------------
Posted to Phorum via PhorumMail

Howdy, Stranger!

Categories

Poll

Top Posters