diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016453.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016453.html | 115 |
1 files changed, 115 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016453.html b/zarb-ml/mageia-dev/2012-June/016453.html new file mode 100644 index 000000000..f905ffc4f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016453.html @@ -0,0 +1,115 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposed Feature:UiAbstraction4mcc + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposed%20Feature%3AUiAbstraction4mcc&In-Reply-To=%3C4FD8808F.3070301%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016440.html"> + <LINK REL="Next" HREF="016456.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposed Feature:UiAbstraction4mcc</H1> + <B>Steven Tucker</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposed%20Feature%3AUiAbstraction4mcc&In-Reply-To=%3C4FD8808F.3070301%40gmail.com%3E" + TITLE="[Mageia-dev] Proposed Feature:UiAbstraction4mcc">tuxta2 at gmail.com + </A><BR> + <I>Wed Jun 13 13:59:11 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016440.html">[Mageia-dev] Proposed Feature:Backports_update_applet +</A></li> + <LI>Next message: <A HREF="016456.html">[Mageia-dev] Proposed Feature:UiAbstraction4mcc +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16453">[ date ]</a> + <a href="thread.html#16453">[ thread ]</a> + <a href="subject.html#16453">[ subject ]</a> + <a href="author.html#16453">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>*Problem* + +MCC is great, and I would love to be able to admin using it regardless +of whether I am using text interface or gtk/qt. The interface is +completely different in curses than gtk interfaces. Curses version is a +second rate citizen, and Gui is all GTK. A lot of the tools are not +available in curses interface, for instance, I don't see a way to +install software or managing repositories. It would be nice to have qt +version as well as gtk (not a major issue, but would be nice) + +*Possible solution* I have thought how this could be addressed and feel +that in the long term, the best solution would be to have the interface +layer abstracted. So when developing a module, you use the mcc UI +library, so you may call for instance mccGui.pushButton then if you are +running in curses it creates a curses button, if you are in KDE it +creates a QPushButton, if you are in Gnome it creates a GTKButton. This +would take a great deal of work, so I started looking around to find any +existing libraries. The first place I looked was openSuSE as Yast does +exactly what I am describing. In yast, the interface is laid out and +works the same way whether you are using curses, Gtk or Qt. To my +surprise they have put a lot of work into separating their Ui library +from the Yast tools. You can use the library to write curses/gtk/qt +programs that use the appropriate widget as needed, independent of Yast. +We could use the Yast Back end, and adapt our front end to use it. This +option would take the least amount of work, as there are perl bindings +to the yast libraries, and so it would only be the gui layer that would +need reworking. The current gtk only modules could become curses/qt/gtk +modules by changing the gtk calls to yast backend calls. + +Just to be clear, I am not suggesting that we port Yast to Mageia, I am +suggesting we use its Ui abstraction only. I use Mageia over openSuse +for many reasons, but I do admire how well Yast works, and would love to +see similar in Mageia. Perhaps we could start planning the next +generation of MCC ?? + + + Why it would be good for Mageia to include it + +It would provide consistency across terminal and gui administration, and +in doing so provide an easy entry into text based administration for +novices. + +Providing the abstraction layer would mean all modules created will be +available to all users. + +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: </pipermail/mageia-dev/attachments/20120613/c7509498/attachment.html> +</PRE> + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016440.html">[Mageia-dev] Proposed Feature:Backports_update_applet +</A></li> + <LI>Next message: <A HREF="016456.html">[Mageia-dev] Proposed Feature:UiAbstraction4mcc +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16453">[ date ]</a> + <a href="thread.html#16453">[ thread ]</a> + <a href="subject.html#16453">[ subject ]</a> + <a href="author.html#16453">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |