R: Integrate AppMenu into Workspace 4.9
Hi, I really like this idea, expecially because I'm dreaming of a KRunner version that uses voice recognition, so the user could do the main operations (and have access to applications menus) using the voice. But I don't know if there are problems in integrating AppMenu in the next version of Plasma. Luca Tringali >Messaggio originale >Da: afies...@kde.org >Data: 09/02/2012 16.07 >A: >Cc: >Ogg: Integrate AppMenu into Workspace 4.9 > >Hey there! > >It seems that people really likes AppMenu, we have fans of everything >we have done with it so far: >-oxygen-appmenu >-plasmoid >-runner > >So it seems clear to me that we should integrate this technology into >Workspace 4.9, but before we do it would be good to hear opinions >about these questions: > >-Is there any way of integrating oxygen-appmenu without breaking >api-abi? Maybe a second version of the API? >-How the KDED works? >-Is there any plans to extend libdbusmenu-qt to make it export the >menu as a model? >-Do we need something else to complete our support? documentation maybe? >-What is the status of it being merged into GTK ? > >Personally I think that AppMenu is a powerful technology that will >allow us to decide how and when show the menubars which sure will be >handy in the future. > >So, what do you think of AppMenu? >___ >Plasma-devel mailing list >Plasma-devel@kde.org >https://mail.kde.org/mailman/listinfo/plasma-devel > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
R: Re: R: dah-dah-da-daaaaah! synchrotron!
Hi, I stopped writing it, since I discovered it's unseful in the new Plasma Classroom project. In fact, someone (I can't remeber who) said it would be easier to use iTalc. Luca Tringali >Messaggio originale >Da: kde...@unormal.org >Data: 05/11/2011 13.53 >A: >Ogg: Re: R: dah-dah-da-dah! synchrotron! > >Am Donnerstag 06 Januar 2011, 11.23:00 schrieb LucaTringali: > >Morning > >> >(on a side note / as a bit of useless trivia: synchrotron came out of >> >design work i did over the holidays for plasma classroom :) >> >> Talking about plasma classroom, I'm working on a plasmoid that shows the >> screen >> of all the classroom's computers, so the teacher can take a look at them >> directly from >> the desktop. Anyway, I'm having some troubles implementing VNC to remote >> view the screens. Can someone help me on this thing? > >Any news about your work in this plasmoid? > >> Luca Tringali > >thx >mario > >___ >Plasma-devel mailing list >Plasma-devel@kde.org >https://mail.kde.org/mailman/listinfo/plasma-devel > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
R: Regarding login authentication of students by the containment...in KDE Plasma Educational Desktop
Hi Karan, I think option a is the best. Remembering username and password is not so difficult. Maybe there could be problems with little childs, but the teacher can have the list of user/password and help the childs if they forget them. Or the teacher can simply reset the password of some students if forgotten. Luca Tringali Messaggio originale Da: wizard.ka...@gmail.com Data: 14/07/2011 16.39 A: "Aaron J. Seigo", "Aleix Pol", , Ogg: Regarding login authentication of students by the containment...in KDE Plasma Educational Desktop Hi Sooo.. when the student logs in, the custom containment in each student desktop has to authenticate the student with the local classroom server... So we have 2 ways of authenticating the student with the server using kde- telepathy: a) We expect the student to remember his username and password, which he will enter in a KDialog popup box by the containment, and if he enters the username/password correctly( which will be verified by telepathy ), then the KDialog box will disappear and his previous saved layout will be fetched from the server. OR b) We hardcode the username and password for each student's machine, so that a desktop A will always have the same username and password, when desktop A loads its containment, then its hardcoded account will be used to authenticate it with the classroom server, and we then get the student's id number(using a KDialog) to fetch his layout from the server. Option b seems suitable, because students may not remember their details properly...where as in option b they only have to remember their id-number, which in case a student forgets, the teacher would have a backup copy of it. but the BIG Problem with option b is that the a student can type some other student's id number and get other student's previous layout, instead of his own...this will not happen in option a. In both the above cases, we will have to setup the individual accounts(whether they belong to the desktops or the students themselves) initially at the time of classroom environment setup. So I suggest that I continue with option a)..any comments or suggestions? -- regards, Karan Pratap Singh ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
R: Re: [kde-edu]: R: GSoC Plasma Educational Desktop Proposal v0.2
Well, doing exams is the only part Plasma Classroom is missing... I think that this software must be complete, so that every important thing (both teaching and examining) can be done directly from the desktop: I don't know how the situation is in other coutries, but in mine the 80% of teachers does not want to use a computer because they says "It's too difficult" (the funny thing is that many times the teacher asks help to the students to use some software). The only way we can make them use computers, is to create something absolutely simple: having everything on the desktop is the first main step. Post Scriptum: I also think that actually KEduca is dead... I have not been able to find a KDE4 version. And it's stupid to do the entire course on computers, then do exams on paper... Luca Tringali Messaggio originale Da: aleix...@gmail.com Data: 31/03/2011 23.41 A: , "LucaTringali" Ogg: Re: [kde-edu]: R: GSoC Plasma Educational Desktop Proposal v0.2 --> I think we shouldn't mix stuff that much. In my opinion plasma classroom has to be a shell, something that lets you select what do you want to work on. We have applications for exams. If an application for doing exams is needed, that should be a different GSoC. My 2 cents :) aleix - Mensaje original - > Couldn't be added a system for doing exams? Something like KEduca did, > if I remember well... the teacher writes a series of questions with > multiple choices and the students will do them. Then the system > immediately gives the results. > > Luca Tringali > > Messaggio originale > Da: wizard.ka...@gmail.com > Data: 31/03/2011 18.43 > A: , > Ogg: [kde-edu]: GSoC Plasma Educational Desktop Proposal v0.2 > > Hi, > > The earlier email had a language error, so I am reposting. > > Please review my Google Summer of Code proposal for Plasma Educational > Desktop, > Please suggest how I can improve it further and if there are any errors > which I can rectify... > > https://docs.google.com/document/pub? > id=1brvVSCrxkD78K3BkC1HM_bb_SCQGAqjj9FI5VJgRjL4 > > > from > Karan Pratap Singh > IRC nick: kps_foo > Chandigarh, India > > > > ___ > kde-edu mailing list > kde-...@mail.kde.org > https://mail.kde.org/mailman/listinfo/kde-edu ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
R: GSoC proposal : home automation
Nice idea, I would like to help in some way, but I'm awfully busy, so I'll probably do something, but I'm not able to partecipate at GSoC full time. Luca Tringali >Messaggio originale >Da: robin.marsoll...@etudiant.univ-rennes1.fr >Data: 24/03/2011 18.59 >A: >Ogg: GSoC proposal : home automation > >Hi everybody, > >I'm preparing my proposal for GSOC and I want some feedback. > >In last discussion about it, Luca Tringali proposed an integration with Plasma >Media Center, I think it's a very good idea for long term, but for now, >domogik is in way for its 0.10 release, PMC is also expecting its first >release, and my project is only ideas. >So I think it could be preferable to devellop only bases for home automation >with domogik in KDE for the moment, and I could do integration with PCM after >its first release and after this summer, with all time I need to do it. > >I drew some drafts of what could be the plasmoids, and I have for the moment >two plasmoid : one for supervision of house in general, and one for >supervision of a single room in the building. I will upload my drafts soon. > >I'm also thinking for a way to set up a configuration for the home, and since >that is not an item used every day (add a room, add shutters, lamps or heating >...), I think it does'nt have its place in a plasmoid, so in a dedicated app? >Probably, for my point of view. > >And what type of interface should I develop for it? With an other app for >conf, I think I couldn't use dataengine/services of Plasma ? So a kio ? > >I intend to start before the official start of GSoC because I travel a few days >in early june. It is a problem for mentors to work with me before official >start in order to give them a little break after? :D > >And what do you think of this? Too ambitious, not enough? > >Presently, I'm revising my C++ (the easy part) and after, I will learn Qt, but >I must also pass my year in the same time. I would try to join you on IRC this >week-end (pseudo : rmrsllr), if I find time. > >Cheers, >Robin Marsollier >___ >Plasma-devel mailing list >Plasma-devel@kde.org >https://mail.kde.org/mailman/listinfo/plasma-devel > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
R: Re: R: [GSOC] Home automation
>Well, I don’t think so ;) Did you have a look at the web-page of the system? >Home automation is much more than a media center. Sure, but the interface could be put everywhere. Even if the real job is done by another application (a backend may I say) the graphical interface can be done using a plasmoid, and this one could be put into the mediacenter shell, like actually works for choosing the file to view in PMC, or its welcome screen. Media Center could be a very easy interface between the user and the home automation system: it's not the system itself, just a frontend. And, anyway, if you have to choose a computer to install the home automation system, would you choose a laptop, or a mediacenter that, for it's nature, is 24 hours on 24 present and operative in your house? Luca Tringali >Messaggio originale >Da: jul...@svg4all.de >Data: 19/02/2011 20.35 >A: "LucaTringali", >Ogg: Re: R: [GSOC] Home automation > >hi, > >Am Samstag, 19. Februar 2011, 20:11:21 schrieb LucaTringali: >> It would be perfect, in particular talking about Plasma Media Center. >> The mediacenter, infact, will be the "head" of the home automation in the >> next future. > >Well, I don’t think so ;) Did you have a look at the web-page of the system? >Home automation is much more than a media center. It’s about managing a home, >with many rooms. A media center is most likely not distributed over all rooms. >I wouldn’t consider it a 'must have' feature to switch the music your children >are listening to in the next room and stuff like that ;) > >That said, I agree, that the media center should be a part of a home >automation system, but it’s not the most important one. > >bye then >julian > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
R: [GSOC] Home automation
It would be perfect, in particular talking about Plasma Media Center. The mediacenter, infact, will be the "head" of the home automation in the next future. Since I've been busy for some months I don't know what is the actual situation of Plasma media center, anyway, this will be one of the first feature to add to that shell. Luca Tringali >Messaggio originale >Da: robin.marsoll...@etudiant.univ-rennes1.fr >Data: 19/02/2011 16.04 >A: >Ogg: [GSOC] Home automation > >Hi, > >I am a French student in 4th year of university cycle, I aim for next year to >integrate acedemic training of home automation in Rennes. > >I am also a convinced users of FLOSS since 2years and of KDE since SC 4.3. > >I am interrested in ergonomics and other disciplines (I like read Aurélien >Gateau's blog posts and other related stuff for example) , and I think home >automation could improve its ergonomics and concept to be very efficient. > >Typically, in this kind of dashboard, we can found various graphics related on >cumsumption of several element in the house, actual state of some element, >actions buttons and some other stuff . > >Last year, for studies, I had a "research" project whose goal was to realize a >draft of a dashbord to be use daily in home automation, so I have basics skills >on what could be realize or not and I can observe that one the main issue of >this type of dashboard is they are design to only show information related to >home automation when they should be integrated in the center of our use of >cumputering, and I think Plasma could do it easily. > >I am currently talking with folks of Domogik¹, a free home automation server. > >Do you think it could be possible with the plasma technologies and what do you >think about this idea in general ? >I am not aware of other implementation of the concept I have exposed and I >know that would be very innovative and with some work of reflexion, but that's >a part of what attracks me. > >I will join you on IRC in coming days, i couldn't for the moment but I wanted >anymay to expose my idea and collect some opinions. > >¹ : http://www.domogik.org/ >-- > >Robin Marsollier >M1 Électronique et Télécommunication - Université de Rennes 1 >___ >Plasma-devel mailing list >Plasma-devel@kde.org >https://mail.kde.org/mailman/listinfo/plasma-devel > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
R: dah-dah-da-daaaaah! synchrotron!
>the subject line of this email should be sung to the tune of your favourite >superhero t.v. show, such as Italian Spiderman. love it! >* how to automatically check for addons from synchrotron on first-run >* how to check for updates so we can offer an auto-update service > >i'd like to make this easy for DataEngine and Plasmoid developers to take >advantage of, preferably by putting such logic right into DataEngine and >Applet itself. it would be nice to see the logic for this in libattica so that >it can be shared by all kinds of application (imagine starting Palapeli and >having a dozen or two puzzles available, new ones appearing all the time, via >synchrotron in the start up listing!). Seems a good idea. This thing will replace kde-look.org or it will continue existing? >(on a side note / as a bit of useless trivia: synchrotron came out of design >work i did over the holidays for plasma classroom :) Talking about plasma classroom, I'm working on a plasmoid that shows the screen of all the classroom's computers, so the teacher can take a look at them directly from the desktop. Anyway, I'm having some troubles implementing VNC to remote view the screens. Can someone help me on this thing? Luca Tringali ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
questions about PMC
Hello, I took a look at http://techbase.kde.org/Schedules/KDE4/4.6_Feature_Plan and I seen that there isn't Plasma Media Center. So PMC will not be released with KDE 4.6? >From the code present in svn playgroud, I discovered that the applet "mediabrowser" doesn't work, because some lines have been commented... why? Luca Tringali ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
R: Re: getting involved with plasma
Hi Giorgios,happy to see you want to help. There are many ways you can help plasma developing:- Create plasmoids: plasmoid can be created using C++, Python, Ruby, Javascritpt. In thenext KDE version (4.6) it will be possible to create plasmoids with QML. If you want to create plasma widgets really nice in a easy way, I recomend you to learn QML: the Qtsite is really useful (http://doc.qt.nokia.com/4.7/gettingstartedqml.html), then you can see examples of QML plasmoids on SVN (http://websvn.kde.org/trunk/playground/base/plasma/kinetic-declarative/). - Develop Plasma shells: actually we are developing Plasma Desktop, Plasma Netbook, andPlasma Media Center. We are also collecting idea for Plasma Classroom. You can find informations about these projects on techbase. If you need some other particular explanationsjust ask. - Fixing bugs: you can take a look at bugs with bugs.kde.org: register on it and then start to seewhat can you solve. When you have written a solution (and seen that it works) you can submitit using the reviewboard.kde.org service. First of all, take a look at SVN, GIT, and reviewboarddocumentation. I hope to have been useful, thanks for joining us. Luca Tringali Messaggio originale Da: terie...@gmail.com Data: 20/10/2010 14.04 A: Ogg: Re: getting involved with plasma I think you are not taking the right steps. You should first see where in plasma you want to get invoved. You said plasma, what in plasma do you want to do? do you have a specific plasmoid need/idea? (there are already lots of them) Anything else? Then you will look at the appropriate tools and language for it. Anne-Marie i don't want to write doc,translate,promote for plasma.i want to fix bugs in plasma's code/plasmoid to create plasmoids,to help in mailing lists/irc. between plasmoids and plasma's code i am more interesting in plasma's code. as it concerns my chose for plasma,i want to get involved with plasma because (for the moment) it is the most interesting project for me. i didn't find something else so exciting such as plasma. i hearing your advices :) ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
R: QML and Plasma -> progress()
Extremely interesting... this will open new possibilities.
Will these functionalities implemented into PlasMate, to
give developers a simple way to write QML plasma widgets?
Luca Tringali
>Messaggio originale
>Da: notm...@gmail.com
>Data: 16/09/2010 15.11
>A: "Plasma"
>Ogg: QML and Plasma -> progress()
>
>Hi all,
>the status of an AppletScript for writing plasmoids in pure QML is
progressing
>rather well, i thought to write a detailed status report/documentation
before
>significative design problems go too far in the implementation, be patient,
is
>really long, but it can be used as a basis for a future documentation.
>
>* It is now possible to have packages that specify a main qml file, just
like
>js plasmoids.
>
>* Plasma widgets are binded in the QML language, with the Plasma.* prefix
>* QGraphicsLayouts are binded in plasma bindings themselves, it is not going
>to be in Qt sadly (but QGraphicsWidget subclasses are starting to work
pretty
>well with anchors/positioners as well)
>* Plasma::Svg and FrameSvg are implemented as QDeclarativeItem subclasses
>binded as Svg and FrameSvg. in the future plasma widgets are going to be
>reimplemented in QML probably, those will be the classes for theming
>
>To use QML in Plasma there are 2 ways:
>* Plasma::QMLWidget -> i a qgraphicswidget that loads a qml file in it, and
>keeps the context/engine/etc, it shortens an otherwise long and repetitive
>task of loding qml files with eventiual parse error management, to be used
in
>c++ plasmoids, where complex logic is needed.
>* QML AppletScript: to write applets completely in QML, (uses a QMLWidget
>internally)
>* only pure qml applets will have access to the "plasmoid" object? (or, the
>plasmoid object could be registered from QMLWidget, only when it is actually
>descendent of an Applet, but it would have to be in libplasma, instead of in
>workspace/runtime)
>
>* Package: as in js bindings the package name resolution is accessible from
>plasmoid.file()
>
>* Theme: defining a Plasma.Theme{} element in qml will obtain an object with
>the Plasma colors as properties -> should be an object always registered to
>the root context instead? maybe by QMLWidget itself so it is always
>accessible?
>
>* DataEngine: a Plasma.DataSource{} object can be defined in QML, this
>connects to a single dataengine source, das the source, dataengine and
>interval properties. its Data property is a QDeclarativePropertyMap, that
maps
>perfectly DataEngine::Data (but is a qobject, so it can notify all
properties
>that change) to access the time of the tiime dataengine one can do:
>dataSource.data.time .
>This can be used from both qml plasmoids or outside. I'm not completely
>sure it's the right approach, alternatively in the dataUpdated of the
>AppletScript QDeclarativePropertyMaps named as something like
>dataengine+source could be assigned to the root context, connections would
be
>done in the oncomplete{} slot of qml items. uhm... in the end i think i'll
>leave the DataSource approach.
>
>* Service: still to be defined, if Plasma.DataSource is the right way to go,
>it could have a service() method that would essentially call
serviceForSource,
>then bindings for kconfig would be needed, but this part is still fggy to me.
>
>* Something else forgotten?
>
>
>Here is the status of the support to Applet properties and methods:
>
>== Methods that the ql applets should be able to reimplement: ==
>
>* paintInterface -> no, no access to qpainters here (and was quickly
becoming
>deprecated anyways)
>
>* constraintsEvent -> formfactor, location, immutable and currentActivity
>become notifying properties -> property binding
>
>* dataUpdated: DataSource qml item: alternative is to set a
>QDeclarativePropertyMap on dataupdated -> but would be good to use it also
in
>c++ plasmoids
>
>* configChanged() -> qml applet reimplements configChanged() function in
root
>Item
>
>* popupEvent() -> qml applet reimplements popupEvent() function in the root
>Item
>
>== Plasmoid functions/properties ==
>
>Unique "plasmoid" oject registered in the root context
>shamelessy copied from the js bindings has the following stuff:
>
>--properties (AppletInterface):
>
>* aspectRatioMode
>* formFactor NORIFY formFactorChanged()
>* location NOTIFY locationChanged()
>* currentActivity NOTIFY contextChanged()
>* shouldConserveResources
>* activeConfig
>* busy
>* backgroundHints
>* immutable NOTIFY immutableChanged()
>* userConfiguring
>* apiVersion CONSTANT
>* rect
>* size
>
>--properties (PopupAplletInterface):
>
>* popupIcon -> needs QIcon bindings for QML
>* passivePopup
>* popupWidget -> is it useful there?
>
>Should all properties that are not CONSTANT have a NOTIFY signal? that is
>needed for qml property binding.
>
>--methods (AppletInterface):
>
>* void setFailedToLaunch(bool failed, const QString &reason = QString())
>* void setConfigurationRequired(bool needsConfiguring, const QString &reason
=
>QString())
R: Re: I: Re: R: Re: plasma classroom
>Don't let people dream to much. Do something let some people work with it and >see how it works. Obiously we cannot do everything they will ask, but we can try to make real the main ideas. That's because, in my experiences, I seen that only teachers knows what they really need. More than that, if we ask them what they need and we realize it, they will use Plasma Classroom: it's like we build the solutions just for them. This could be a big opportunity to make a lot of teacher turn from propietary software to KDE and GNU/Linux. But we need to encourage them, giving what they want. Else we will do the same error that Microsoft does: creating things without thinking about the people that will use them. Luca Tringali >Messaggio originale >Da: kde...@unormal.org >Data: 15/09/2010 8.26 >A: >Ogg: Re: I: Re: R: Re: plasma classroom > >Am Dienstag 14 September 2010, 19:51:08 schrieb LucaTringali: > >Morning > >> >i'd rather see the suggestions go somewhere else >> >rather than flood this mailing list. >> >> Ok, the suggestions could be stored everyone in an >> html page. What do you prefer? >> >> >other than that, it's a reasonable idea. could you set >> >this up on a web server somewhere and perhaps >> >store the results in a database or somesuch that we >> >could then grab it from later? >> >> Sure, but it's better if it's stored on a KDE server: it >> would be more official, and other people could help >> translating it. I can create a tar file with all: you will >> just need to upload its content on a webserver. > >Don't care about to many opinions. The school system and education is such a >big institution and has such different situations and wishes. You only get >distracted by too many opinions and ideas. And if you once have some real >working code it's much more concret for teacher and education specialist to >see what's possible. > >Don't let people dream to much. Do something let some people work with it and >see how it works. > >I think it's important that you have some school(s) or teachers and try to fit >their needs as good as possible. Plasma is such a flexibel framework that you >still can adjust it for other environments and situations. > >If and when you satisfy the needs of the brasilian school(system) you've done >such a big task. > >Just IMHO >Mario >___ >Plasma-devel mailing list >Plasma-devel@kde.org >https://mail.kde.org/mailman/listinfo/plasma-devel > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
R: Re: R: Re: plasma classroom
>On Tuesday, September 14, 2010, LucaTringali wrote: >> It will send to this mailing list a message containing the suggestion >> submitted by a teacher. > >actually, ignore my previous email. let's set up an area on forum.kde.org >for Plasma Classroom feedback. the forum admins are really quite open >to such things IME. forum.kde.org already exists and would be a great way >to draw more people (e.g. teachers) closer into our community. That's good, but I think that many teachers don't like to subscribe to a forum just to post a message. I thought about that simple form because in this way a teacher can submit his/her idea without any kind of obligation (like subscribing to a forum): in 5 minutes he/she can help us. Obiously we can suggest to this people that if they want to help a little more they can use our forum, but the biggest part of teachers will not like to "waste" their time. Anyway, if you really want to use the forum, I suggest to create a section dedicated to this initiative, and a redirect link easy to remember (like www.kde. org/classroom/) so that it's easy to tell it to teachers (Obiously if the address is forum.kde.org/viewforum.php?f=199&sid=da79038763865ecbb8e65dc479b2c5bc you see that it's difficult to remember and less attractive). Luca Tringali ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
I: Re: R: Re: plasma classroom
>i'd rather see the suggestions go somewhere else >rather than flood this mailing list. Ok, the suggestions could be stored everyone in an html page. What do you prefer? >other than that, it's a reasonable idea. could you set >this up on a web server somewhere and perhaps >store the results in a database or somesuch that we >could then grab it from later? Sure, but it's better if it's stored on a KDE server: it would be more official, and other people could help translating it. I can create a tar file with all: you will just need to upload its content on a webserver. Luca Tringali ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
R: Re: plasma classroom
> Another idea i had is to create a webpage from
> which teachers of all the world can submit
> suggestions for this project.
>that would also be really great; setting up a community around this could be
key, and get an early-adopter / feedback community started would be excellent.
>if a wiki would be enough, we can use community.kde.org/Plasma/Classroom as a
starting point, and populate it with more teacher-user oriented links and info?
I thought at a form like this:
Create a file called "submityouridea.php":
';
print $textlang;
print '';
print 'Deutch';
print 'English';
print 'French';
print 'Italian';
print '';
print ' ';
$schooltype = $_POST['schooltype'];
$country = $_POST['country'];
$suggest = $_POST['suggest'];
$email = $_POST['email'];
$person = $_POST['person'];
if ($suggest!=""){
$suggestion = 'This is the idea suggested by '.$person.', that teaches in a
'.$schooltype.' in '.$country.'. The suggestion is:'.$suggest.' We
can contact this teacher by the e-mail: '.$email;
if( @mail("tringalinv...@libero.it", "plasma-classroom suggestion",
$suggestion) ) print ''.$textgood.'';
else print ''.$textwrong.'';
}
print '';
print $textperson;
print '';
print $textschool;
print '';
print ''.$schoola.'';
print ''.$schoolb.'';
print ''.$schoolc.'';
print ''.$schoold.'';
print '';
print $textcountry;
print '';
print $textsuggest;
print '';
print $textplease;
print '';
print $textemail;
print '';
print ' ';
?>
then create a file called "english.php":
It will send to this mailing list a message containing the suggestion
submitted by a teacher.
Try it opening the file submityouridea.php with the browser.
Luca Tringali
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
plasma classroom
Hello everybody, yesterday took place a Plasma irc meeting. I was busy, so I want to say some words now, about Plasma Classroom: I think it's time to set up a folder on svn for this project. It could be created cloning the folder of plasma-desktop, so everyone could start writing code and discuss it with reviewboard. Another idea i had is to create a webpage from which teachers of all the world can submit suggestions for this project. Luca Tringali ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
R: Re: [kde-promo] Plasma Media Center Branding
That's absolutely right. >Messaggio originale >Da: ase...@kde.org >Data: 15/07/2010 18.03 >A: , >Ogg: Re: [kde-promo] Plasma Media Center Branding > >On July 15, 2010, Stuart Jarvis wrote: >> Alternatively, maybe we have the app which is called $something and can >> run anywhere and also a very simple Plasma Media Center workspace for >> full-time Media Center pcs that pretty much Plasma Desktop with different >> defaults: no panels and maybe just a couple of system monitor widgets, a >> button to launch $something and that launches $something full screen on >> login. > >you've just described exactly what PMC will be. :) > >it can be used as: > >* a media center augmentation to Plasma Desktop or Netbook. in this case, it >runs as a full-screen app and "takes over" the computer's display and >interaction while running. kind of like a screen saver, only for media >services and without requiring a password to exit. > >* the workspace itself. in such cases, launching random apps probably isn't >part of the desired use cases, though that could indeed be supported fairly >easily if it ended up falling into scope. generally, in this usage it would be >used on a dedicated media center device connected to a large screen (t.v., >projector, etc.) and used for media playback / storage exclusively. > >as such, i think the branding works as Plasma Media Center since in both use >cases it becomes the work space one is interacting with. in the first use >case, it's a temporary "overlay" while in the second case it is indeed the >full workspace. in both cases, it's the exact same binary being run. > >-- >Aaron J. Seigo >humru othro a kohnu se >GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 > >KDE core developer sponsored by Qt Development Frameworks >___ >Plasma-devel mailing list >Plasma-devel@kde.org >https://mail.kde.org/mailman/listinfo/plasma-devel > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
