Hello all! Firstly let me start off by saying my knowledge of flex is 
fairly limited - but my knowledge of flash and AS are as i would 
describe as intermediate/advanced. Before i get into it - i just want 
to make clear to everyone that, no - im not trying to phish for 
someone to do this for me, i very much would like to learn for 
myself, i just need direction! lol.  So any thoughts, suggestions, 
tactics! i would greatly appreciate it all!

I am trying to create an app for a community im involved with in 
which we produce a monthly eZine. We have a team of some 20-30 people 
working on different articles and content. What I am trying to 
accomplish is build a very superficial CMS in essence. An online app 
where firstly, the editor can specifiy the content for the upcomming 
month (i.e what needs to be done) the team members may then submit 
their articles and so forth for each section specified by the editor, 
and finally where I (the publisher in this case) can view each piece 
to finally compose a finished eZine. All this - each month!

Here is a little of my thought proccess.

Start with a Login screen. This is where i would split up the various 
roles, allowing access to different parts of the app depending on 
their role. The editor would be able to go the an admin section 
where, each month, she may specifiy which sections are going to be 
included this month. The team would be able login to see what needs 
to be done each month, sign up for it, do it, then submit it. And 
where the publisher can view what should basically be a summary of 
the content submitted both thus far, and finally.

For the editor, I would have a list of all the possible sections that 
could be included at any given time. Beside which would be a panel 
with a list for what is to be included this month (i was thinking a 
drag and drop from the list of possibles, over to the list of "to be 
included") once she is satisfied with the content she has layed out, 
she could hit save, and the list she dragged to ("to be included") 
would be saved. 

Team members would then see a list on the left with all the sections 
needing to be done this month. Then some sort of system...be it color 
coded, tick box, something to allow people to see what is being done, 
whats completed, and what needs to yet be done, as well as what 
has/has not been proofed by the checkers (explain about them later). 
Perhaps when an item on the list is selected on the right it would 
load up a few things: at the top a tick box reading "proof read" 
(that only the checker role would be able to modify, but all could 
see) if no one is yet signed up to do the selected item, there would 
be a button they could sign up, which (based on their login name) 
would assing them to that article and the article would then only 
display who is doing it, not the button. and then a text box for 
copy/pasting or typing in the article, and a field for uploading 
images for the article. They could then save it. If the article has 
no one assigned to it, the text box would be greyed out, and if 
someone is viewing it that is not assigned to be doing it, they can 
only read - not modify. (unless they are a checker).

Checkers would be able to modify all the articles, as well as sign 
off on the article, by ticking the check box (perhaps adding their 
name beside it so we know who proof read it, maybe not), as well as 
apply to do articles themselves.

Publisher, would be able to login and have a summary button in which 
all the content is compiled into one long document broken down by 
headings so i know what is what, and can then bring into inDesign for 
publishing.

Now, i know this is not a simple undertaking - and I have been 
fiddling with ideas and what not. I was toying with text files, or 
xml, all of which i have pretty much ruled out - not to mention the 
fact i have had no luck with roles and such with a login, other than 
by declairing simple "if" statements. Not ideal by any means. I have 
managed to get a simple upload script working - nothing exciting 
there, nor entirely usefull at this point.

I am using this as a method for me to learn, becase i learn by 
jumping in at the deep end. And to be completly honest - up to this 
point i have been slightly regretting the afformentioned metophor. If 
anyone has any idea, or better yet! the drive and enthusiasm to team 
up with me on this, I couldnt be happier. Anything anyone can offer 
would be great! After all, im floundering here! Cheers everyone - and 
thanks for staying with me up till now.

--][-- 

Reply via email to